Media values can now expose their content through the MEDIA_CONTENT navigation key. Inline payloads are returned directly; referenced payloads are loaded and validated. Tests cover missing paths, unavailable content, and query behavior.

Changes: Media Content Navigation

Layer / File(s)	Summary
Resolve media content baml_language/crates/btel_reader/src/value.rs, baml_language/crates/btel_reader/src/value/span.rs, baml_language/crates/btel_reader/src/value/span/tests.rs, baml_language/crates/baml_query_btel/tests/values.rs, baml_language/crates/baml_builtins2/keyword_docs/baml_keywords.yaml	The MEDIA_CONTENT key resolves inline content or loads and validates content from a referenced child blob. Tests cover supported and missing paths, unavailable content, descriptor rendering, and query filtering. Query documentation describes media content access.

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Feature

Sequence Diagram(s)

sequenceDiagram
  participant BtelQuery
  participant ValueStep as value::step
  participant MediaText as span::media_text
  participant ChildBlob
  BtelQuery->>ValueStep: Navigate to MEDIA_CONTENT
  ValueStep->>MediaText: Resolve media payload
  opt External payload
    MediaText->>ChildBlob: Load referenced content
    ChildBlob-->>MediaText: Return child content
  end
  MediaText-->>ValueStep: Return content or navigation result
  ValueStep-->>BtelQuery: Return navigation result

Loading

Suggested reviewers: 2kai2kai2, hellovai

Merge Risk: Minimal · up to 65875

This change lets queries read a media value's content as base64 text. Its behavior is covered by unit and query tests, and no merge-blocking risk was identified.

Security architecture risk: Low · up to 65875

Explicit queries can now return captured media content. Existing redaction, integrity checks, and read budgets remain in place, and no boundary bypass was identified. Access controls in the consuming application were not available for verification.

Retained concerns
No architecture-level concerns identified.

Security review details

Security Blast Radius

• inferred — At the inspected query layer, the exposure expands to captured media reachable through value navigation in the configured project's CAS. The change does not itself introduce a new network destination, arbitrary media-file read, or additional service credential. Remote consumer authorization and tenant isolation remain outside the inspected scope.

Trust Boundaries and Controls

• observed — User-selected query paths reach the new payload read through the existing read-only query machinery. The SQL translator accepts only one query statement, and SQLite authorization denies non-read actions and privileged file or extension functions. These controls constrain execution authority but do not establish who may access a project's captured payloads.

Resilience and Maintainability Implications

• observed — The existing string-scalar path returns complete text rather than applying the structured-render text cap. The new media path inherits this behavior. Default CAS reads are capped at 64 MiB, and default query output and duration budgets remain enabled; however, output size is checked after collecting a row, so that budget is not a strict peak-memory ceiling.

Pre-merge checks: 4

Check name	Status	Explanation
Title check		The title "Read a media value's content with ['base64']" matches the main change. The PR adds a query path ending in ['base64'] that reads media payloads as base64 text, including content in child CAS…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.

Full details: Title check

Explanation

The title "Read a media value's content with ['base64']" matches the main change. The PR adds a query path ending in ['base64'] that reads media payloads as base64 text, including content in child CAS blobs. The raw summary confirms the same behavior in the query docs, the btel_reader span navigation, and the new tests. The title is short, specific, and does not list files.

Generate unit tests (beta)

• Commit to this branch
• Create a new PR

Violations:

• packed-program (Linux) file_bytes: 39.3 MB exceeds limit of 30.1 MB (exceeded by +9.2 MB, policy: max_file_bytes)
• packed-program (Linux) file_delta_pct: +34.9% exceeds limit of 3.0% (exceeded by +31.9pp, policy: max_delta_pct)
• bridge_wasm (WASM) gzip_bytes: 7.7 MB exceeds limit of 5.9 MB (exceeded by +1.9 MB, policy: max_gzip_bytes)
• bridge_wasm (WASM) gzip_delta_pct: +36.5% exceeds limit of 3.0% (exceeded by +33.5pp, policy: max_delta_pct)

Add/update baselines:

.ci/size-gate/wasm32-unknown-unknown.toml:

[artifacts.bridge_wasm]
file_bytes = 26145178
gzip_bytes = 7727648

.ci/size-gate/x86_64-unknown-linux-gnu.toml:

[artifacts.packed-program]
file_bytes = 39318808
gzip_bytes = 16161060